CU Amiga Super CD-ROM 2/CU Amiga Magazine's Super CD-ROM 02 (1996)(EMAP Images)(GB)[!][issue 1996-04].iso/magazine/amiga_e/amigae.july.archive/000075_crash!cislabs.pitt.edu!cjfst4_Mon, 26 Jul 93 13:49:50 PST.msg

Text File | 1993-08-31 | 2KB | 37 lines

Received: by bkhouse.cts.com (V1.16/Amiga)
    id AA00000; Mon, 26 Jul 93 13:49:50 PST
Received: from phantom.cislabs.pitt.edu by crash.cts.com with smtp
    (Smail3.1.28.1 #15) id m0oKYis-0000MsC; Mon, 26 Jul 93 13:00 PDT
Received: from meg.cislabs.pitt.edu by phantom.cislabs.pitt.edu (4.1/1.34)
    id AA13217; Mon, 26 Jul 93 16:00:27 EDT
Received: by meg.cislabs.pitt.edu (4.1/EMI-2.1)
    id AA00849; Mon, 26 Jul 93 16:00:24 EDT
Message-Id: <[e-mail]>
Date: Mon, 26 Jul 1993 16:00:24 -0400 (EDT)
In-Reply-To: <[e-mail]> from "[e-mail]" at Jul 26, 93 11:18:08 am
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 734
From: [e-mail]
To: [e-mail] (Amiga-E List)
Subject: Re: CHIP specifier

>
> I would also greatly appreciate a chip specifier. What are
> the advantages of storing this sort of data in a separate
> file? IMO, it only creates problems for the end-user when
> they come to copy your product to their hard disk or
> whatever.
>
> Why not give the compiler a command-line option to
> incorporate graphics/sound files into the finished
> program. E could give the program a pointer to a
> structure which tells it where the memory is etc. In this
> way, Amiga E could achieve a 'memory bank' type operation
> which is what has helped AMOS become so incredibly
> popular. What do you think Wouter? Is this feasible?

I requested this when E first came out (remember Wouter?) and _still_
think its a good idea.